-
Notifications
You must be signed in to change notification settings - Fork 14.8k
vulkan: Replace deprecated VK_EXT_validation_features #17637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
3db03c6 to
82b3726
Compare
|
FWIW I've never found it necessary to use GGML_VULKAN_VALIDATE, I always enable VVL either by setting the env var VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validation or by opening the Vulkan Configurator (which also has a check box to easily enable debugprintf). However, this change looks correct to me, and I don't object. |
Thanks for the input. I didn't know of the correct approach so was using |
|
I don't think either way is necessarily more correct, one is just a programmatic interface and the other is user-driven. I don't have a strong preference about whether to remove it. |
|
Actually I realized that using the programmatic interface has some benefits in debugging where you can just compile it with debug print and provide the binary to someone else for reproduction. No need for external tweaking so less confusion and less human errors. |
* replaced deprecated VK_EXT_validation_features * forgot to remove old code
* replaced deprecated VK_EXT_validation_features * forgot to remove old code
* replaced deprecated VK_EXT_validation_features * forgot to remove old code
* replaced deprecated VK_EXT_validation_features * forgot to remove old code
When enabling
-DGGML_VULKAN_VALIDATE=ONI see lots of validation warnings cluttering the output. I want to remove at least one of them by replacing the deprecatedVK_EXT_validation_featureswithVK_EXT_layer_settings. This should also make it easier to enable the Debug Printf feature which makes debugging the shader much easier (at least for me)Before
After